Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1017

reference
443-tree-1
name
1017
tree-preservation-order

undefined

443-tpo-1
uprn
address-text
point
POINT (-1.023983 50.897567)
geometry
MULTIPOLYGON (((-1.023898 50.897558,-1.023901 50.897574,-1.023913 50.897589,-1.023932 50.897602,-1.023955 50.897609,-1.023982 50.897612,-1.024008 50.897610,-1.024032 50.897602,-1.024051 50.897591,-1.024064 50.897576,-1.024068 50.897559,-1.024064 50.897542,-1.024053 50.897527,-1.024034 50.897515,-1.024010 50.897507,-1.023984 50.897504,-1.023958 50.897507,-1.023934 50.897514,-1.023914 50.897526,-1.023902 50.897541,-1.023898 50.897558)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL